Managing devices associated with a digital wallet account

ABSTRACT

Managing user devices associated with a digital wallet account comprises associating, using one or more computing devices, one or more user computing devices with a digital wallet account of a user, each of the associated one or more user computing devices being activated to conduct financial transactions with a merchant utilizing the digital wallet account; presenting the associated user computing devices in a list of associated user computing devices; receiving a request to deactivate a particular user computing device from the list of associated user computing devices; deactivating the particular user computing device, the deactivation being sufficient to prevent the user computing device from conducting transactions with a merchant utilizing the digital wallet account; and presenting a deactivated status of the particular user computing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to U.S. Provisional PatentApplication No. 61/678,089, filed Jul. 31, 2012 and entitled “Proxy CardSystem.” The entire disclosure of the above-identified priorityapplication is hereby fully incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to digital wallet transactions,and more particularly to managing devices associated with a digitalwallet account.

BACKGROUND

Digital wallet accounts can be configured by a user for transactionswith merchants. The transactions can be conducted online or offline.Digital wallet accounts can be used for online purchases via theInternet with a user computing device. A digital wallet applicationmodule can be installed on a mobile computing device for use in offlinepurchases. For example, the user can utilize a digital walletapplication module on a user computing device to make purchases at amerchant location via near field communication (“NFC”), BLUETOOTH,Wi-Fi, or other proximity communication technologies.

The digital wallet account can be associated with a proxy card account.Proxy card payment systems enable users to utilize a single card toaccess multiple financial accounts maintained by multiple issuers. Theuser receives a proxy card from the proxy card system and either createsa new proxy card system account or associates the proxy card with theuser's digital wallet account already maintained by the proxy cardsystem. The user then associates one or more financial card accountswith the proxy account. For example, the user can associate with theuser's proxy card account multiple debit/credit cards maintained bymultiple issuers (including the proxy card system operating as anissuer), stored value cards (for example, gift cards, prepaid cards,re-loadable transaction cards, exchange cards, and other forms ofnon-credit based value cards), loyalty cards or store rewards cards,value added service accounts (for example, coupons, vouchers for prepaidoffers, redemption offers, and other forms of offers), peer-to-peertransaction accounts, bank accounts and/or other forms of financial cardaccounts.

In a conventional digital wallet application, the user is not able todisable a digital wallet application module on a different mobile userdevice or other user device. For example, a user might lose a mobilephone that has a digital wallet application module installed or havethat cell phone stolen. The user does not have a manner of convenientlydisabling or removing the user device from the list of authorizeddigital wallet devices.

SUMMARY

Techniques herein provide a computer-implemented method to manage userdevices associated with a digital wallet account. A payment systememploys a server configured for associating, using one or more computingdevices, one or more user computing devices with a digital walletaccount of a user, each of the associated one or more user computingdevices being activated to conduct financial transactions with amerchant utilizing the digital wallet account; presenting the associateduser computing devices in a list of associated user computing devices;receiving a request to deactivate a particular user computing devicefrom the list of associated user computing devices; deactivating theparticular user computing device, the deactivation being sufficient toprevent the user computing device from conducting transactions with amerchant utilizing the digital wallet account; and presenting adeactivated status of the particular user computing device.

Another aspect of the example embodiments described herein provides acomputer program product that is installed on a server to manage userdevices associated with a digital wallet account. The computer programproduct includes a non-transitory computer-readable storage devicehaving computer-readable program instructions stored therein. Thecomputer-readable program instructions include computer programinstructions for associating each of the associated one or more usercomputing devices being activated to conduct financial transactions witha merchant utilizing the digital wallet account; presenting theassociated user computing devices in a list of associated user computingdevices; receiving a request to deactivate a particular user computingdevice from the list of associated user computing devices; anddeactivating the particular user computing device, the deactivationbeing sufficient to prevent the user computing device from conductingtransactions with a merchant utilizing the digital wallet account.

These and other aspects, objects, features and advantages of the exampleembodiments will become apparent to those having ordinary skill in theart upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for managing devicesassociated with a digital wallet account, in accordance with certainexample embodiments.

FIG. 2 is a block flow diagram depicting a method for adding a userdevice to a digital wallet account, in accordance with certain exampleembodiments.

FIG. 3 is a block flow diagram depicting a method for disabling orremoving a user device from a digital wallet account, in accordance withcertain example embodiments.

FIG. 4 is a block flow diagram depicting a computing machine and amodule, in accordance with certain example embodiments.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS Overview

The example embodiments provide a digital wallet account and one or moreuser devices utilized to make transactions with the digital walletaccount. To receive the benefits of the techniques described herein, incertain embodiments, the user will install an application, use aparticular service, or otherwise engage in the techniques herein. In theexample embodiment, a digital wallet account includes specifiedinformation for one or more financial accounts, including, but notlimited to debit cards, credit cards, stored value cards,loyalty/rewards cards, bank accounts, peer-to-peer transaction accounts,stored value accounts, and coupons (including purchased offers and otheroffers), each accessible by a digital wallet application module or otherembodiment of the digital wallet account. In an example embodiment, theuser can access the digital wallet account using an applicationoperating on a mobile communications device or other device equippedwith a web browser or other communication module and connected to theInternet. The digital wallet account can be hosted by a paymentprocessing system or any other suitable system.

In an example embodiment, the digital wallet account can utilize orrepresent a proxy card account. The digital wallet account can store theproxy card account or any suitable representation or operations of theproxy card account. The proxy card account can be a function of thedigital wallet account or can represent the system by which the digitalwallet account operates. Alternatively, a proxy card account can be justone of multiple accounts managed and utilized by the digital walletapplication module.

In an example embodiment, a front-end “kill-switch” provides aninterface for users to display, monitor, and de-activate their wirelessand physical proxy card devices on a per-device basis. Thisimplementation provides security and control to payment processingsystem users.

Wireless devices and other user devices are added to a digital walletaccount when the user device sends a request to the payment processingsystem to add the user device. User devices added to the digital walletaccount can include any computing device available to a user including adesktop computer, laptop computer, tablet computer, a television withone or more processors embedded therein and/or coupled thereto, smartphone, handheld computer, personal digital assistant (“PDA”), or anyother wired or wireless, processor-driven device. The digital walletaccount may be represented on a device as a digital wallet applicationmodule, a digital wallet application module operating on a website orserver, a representation on a user interface of the payment processingsystem, or any other suitable embodiment of the digital wallet account.

Additionally or alternatively, the digital wallet account may include aphysical payment card, including a proxy card, or other physical toolfor conducting transactions, such as a magnetic stripe card, smartcard,RFID device, or other suitable tools. Throughout the specification,“digital wallet application module” will be intended to encompass allembodiments of the digital wallet account on user devices, includingphysical cards. Additionally, “user devices” will be intended toencompass all suitable devices used to host a digital wallet accountembodiment, including physical cards.

In an example embodiment, a request for adding a user device is requiredwhen a digital wallet application module is first installed and aftereach reset. Thus, the first activation is when the application is firstset up on the user device. A subsequent reset and re-activation of theapplication will be considered a new activation. In an exampleembodiment, re-activation of a deactivated device is performed byreinstalling and setting up the digital wallet application module on theuser's mobile communication device. In an example embodiment, the usermay be required to re-enter their financial payment card information.

In an example embodiment, a page on a user interface associated with adigital wallet account provides a listing of user devices associatedwith the digital wallet account. The device listing will indicate theenabled user devices that the user owns and the activation state of eachdevice. The device list contains all of the information required torender a virtual representation of the device to the user. For example,the device list may show information indicating the device status suchas the device name, the activation date, the last time a transaction wasinitiated, the activation status, a device image, an option todeactivate any active devices, an option to retry a deactivation if aprevious attempt did not complete, and any other suitable displays oroptions.

In an example embodiment, the user can access the digital wallet accountby logging onto the payment processing system website online, using adigital wallet application module on a user mobile communication devicesuch as a user device, or by using any other suitable user interfacesystem. The user may retrieve the status of all devices linked to thedigital wallet account.

The user can select a user device to add to the digital wallet accountby adding the user device details into a user interface of the digitalwallet account. For example, the user can enter the phone number to amobile user device and the digital wallet account can locate theappropriate user device over the network, via email, over a wirednetwork, or via any other suitable manner. The user can select thedevice from a list of devices associated with the user. The user canselect a device from a list of inactive devices. Any other suitablemanner of selecting user devices to add to the digital wallet accountcan be employed.

The user can install the digital wallet application module on the userdevice. In an example embodiment, the payment system can transmit thedigital wallet application module to the user device. In anotherexample, the user device can locate the digital wallet applicationmodule on the Internet and download the application for the digitalwallet application module. In another example, the user device candownload the digital wallet application module from a website of thepayment processing system. The user can install the digital walletaccount in any other suitable manner.

In an alternative embodiment, the user device has installed a digitalwallet application module before the user device is added to the devicelist of the digital wallet account. Additionally or alternatively, theuser can use the digital wallet application module to add the device tothe device list. For example, the user can open the digital walletapplication and input the digital wallet account credentials to enterthe digital wallet account. From the user device, the user can add theuser device to the digital wallet account. For the purposes of fraudprevention, the user would be required to authenticate the addition ofthe user device.

When a user adds a user device to the device list on the digital walletaccount, the digital wallet application module on the user devicetransmits a setup request to the payment processing system. If notpreviously authorized, the user can enter security information toauthorize the addition.

The user device can then be added to the device list on the digitalwallet account. The device list can display the user device on the listwith any additional identification or visual representations of the userdevice that are configured by the user or the digital wallet account.For example, the device list can display the user device phone number,serial number, username, or any suitable alias or identificationprovided by the user or others. The device list can display a picture orother representation of the user device, such as a picture of the modelof the device based on provided model numbers. Any other suitabledisplay or identification can be used to represent the user device onthe device list.

The device list can display the status of the user device as active orany suitable description of the status.

The user may desire to remove a user device from the digital walletaccount. The user may desire to disable a digital wallet applicationmodule from a particular user device if that user device is stolen,lost, or otherwise has the security of the user device compromised. Theuser may desire to remove a user device if the user device is beingtraded, sold, or replaced. The user may desire to remove a user deviceif the user device is no longer going to be used for digitaltransactions or for any other suitable reason.

The user can open the device list on a user interface of the digitalwallet account in the manner employed to add a device. The user canaccess the digital wallet account by logging onto the payment processingsystem website online, using a digital wallet application module on amobile communication device, or by using any other suitable userinterface system.

The user can select a user device to remove from the list. The user canidentify the desired user device by selecting the representation of theuser device from the list. For example, the user can click on a pictureof the user device on the user interface. The user can tap a username oridentifier of the user device on the user interface. The user can statea verbal identification of the device to select the user device. Anyother suitable manner of selecting the user device from the list can beemployed.

When deactivation is initiated, the digital wallet user interface beingutilized transmits the deactivation request to the payment processingsystem and the user device that is being deactivated. The paymentprocessing system can receive the request and deactivate the user devicefrom a list of active devices within the payment processing system. Thepayment processing system will no longer honor requests for transactionsfrom the digital wallet application module operating on the deactivateduser device.

In an example embodiment, the user device that is being deactivated onthe device list is not contacted to disable the digital walletapplication module because it is not currently connected to acommunication network. The deactivation can occur when the user devicenext achieves network access. That is, when the user device is againturned on, returned to a service area, or otherwise achieves a networkconnection, the instructions can be transmitted at that time to thedevice to be deactivated. If the user device successfully communicateswith the payment processing system server, then the digital walletapplication module on the user device is deactivated and the digitalwallet application module can no longer be utilized for transactionsusing the digital wallet account of the user. In an alternateembodiment, the digital wallet user interface being utilized for thedeactivation or the payment processing system transmits the deactivationrequest directly to the user device that is being deactivated.

The digital wallet application module also can be removed from a userdevice that has been deactivated from the digital wallet account. In anexample embodiment, the digital wallet account can transmit instructionsto the user device to delete the digital wallet application module, todelete the digital wallet account information, to delete financialaccount information from the user device, or to delete any othersuitable information that could be used to make the digital walletapplication module operable with the digital wallet account of the user.Additionally or alternatively, the user can manually delete the digitalwallet application module or other information from the user device.

When deactivation is initiated, the user interface will provide a clearindication to the user of what is happening, and what, if any, furtheraction must be taken. The user interface displays to the user that thedeactivation is successful or if the deactivation is in progress. Forexample, the user interface can display that a device is partiallydisabled.

In certain instances, a partially disabled state can be created when thepayment processing system can be updated, but not the user device. Whenthe digital wallet account is unable to contact the user device, thedigital wallet application module on the user device cannot be deletedor disabled. Moreover, if the user has a stored value card on a userdevice that is partially disabled, then the user may still be vulnerableto charges on the stored value card, and the user will need to contactthe issuer of the stored value card to disable the card. The userinterface will display to the user that the digital wallet account willretry the deactivation button until a complete deactivation is achievedor the digital wallet account is requested to discontinue thedeactivation.

If a user device has been deactivated on the digital wallet account atthe payment processing system but the digital wallet application moduleon the user device has not been deactivated, a transaction might beattempted by a person in possession of the user device. For example, ifa user device is stolen, the person with the stolen device may attempt atransaction. The payment processing system is notified of thetransaction request. However, the payment processing system determinesthat the user requested to have the user device deactivated on the userdevice list. The payment processing system declines the transaction andattempts again to deactivate the digital wallet application module onthe user device.

The user interface also can allow the user to remove any deactivateddevices from the list of devices, or the removal can occurautomatically. Devices that have been deactivated can appear in the listin a disabled state until the user manually deletes them. Additionallyor alternatively, the user can leave the deactivated devices on the listof devices or store the deactivated devices in a list of deactivated orunused devices.

Additionally or alternatively, the deactivated device can remain on thelist of devices but remain hidden from view until the user requests thathidden devices be displayed. In an example embodiment, devices that aremarked hidden will not be shown, except when showing a historic deviceview is requested.

Example System Architectures

Turning now to the drawings, in which like numerals represent like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a system for managing devicesassociated with a digital wallet account, in accordance with certainexample embodiments. As depicted in FIG. 1, the system 100 includesnetwork devices 110 and 140 that are configured to communicate with oneanother via one or more networks 105.

Each network 105 includes a wired or wireless telecommunication means bywhich network devices (including devices 110 and 140) can exchange data.For example, each network 105 can include a local area network (“LAN”),a wide area network (“WAN”), an intranet, an Internet, a mobiletelephone network, or any combination thereof. Throughout the discussionof example embodiments, it should be understood that the terms “data”and “information” are used interchangeably herein to refer to text,images, audio, video, or any other form of information that can exist ina computer-based environment.

Each network device 110 and 140 includes a device having a communicationmodule capable of transmitting and receiving data over the network 105.For example, each network device 110 and 140 can include a server,desktop computer, laptop computer, tablet computer, a television withone or more processors embedded therein and/or coupled thereto, smartphone, handheld computer, personal digital assistant (“PDA”), or anyother wired or wireless, processor-driven device. In the exampleembodiment depicted in FIG. 1, the network devices 110 and 140 areoperated by end-users or consumers on user devices and paymentprocessing system operators respectively.

The user 101 can use the communication application 112 on a user mobiledevice 110, such as a web browser application or a stand-aloneapplication, to view, download, upload, or otherwise access documents orweb pages via a distributed network 105. The network 105 includes awired or wireless telecommunication system or device by which networkdevices (including devices 110 and 140) can exchange data. For example,the network 105 can include a local area network (“LAN”), a wide areanetwork (“WAN”), an intranet, an Internet, storage area network (SAN),personal area network (PAN), a metropolitan area network (MAN), awireless local area network (WLAN), a virtual private network (VPN), acellular or other mobile communication network, Bluetooth, NFC, or anycombination thereof or any other appropriate architecture or system thatfacilitates the communication of signals, data, and/or messages.

The communication applications 112 can interact with web servers orother computing devices connected to the network 105, including thepoint of sale terminal of the merchant system (not shown), the merchantserver of a merchant system, the web server 141 of the paymentprocessing system 140.

The user mobile device 110 may include a digital wallet applicationmodule 111. The digital wallet application module 111 can encompass anyapplication, hardware, software, or process the user devices 110 canemploy to assist the user 101 in completing a purchase. A digital walletapplication module 111 can interact with a communication application 112or can be embodied as a companion application of the communicationapplication 112. As a companion application, a digital walletapplication module 111 executes within a communication application 112.That is, a digital wallet application module 111 may be an applicationprogram embedded in a communication application 112.

The user mobile device 110 also includes a data storage unit 113accessible by the digital wallet application module 111 and thecommunication application 112. The example data storage unit 113 caninclude one or more tangible computer-readable storage devices. The datastorage unit 113 can be stored on the user mobile device 110 or can belogically coupled to the user mobile device 110. For example, the datastorage unit 113 can include on-board flash memory and/or one or moreremovable memory cards or removable flash memory.

A user 101 can employ physical payment instrument 120 to initiate atransaction employing the digital wallet account 121, a proxy cardaccount on the digital wallet account 121, a specified paymentinstrument operating on the digital wallet account 121, or any otherpayment instrument embodiment. In an example embodiment, a physicalpayment instrument 120 looks and/or functions in the same manner as astandard credit or debit card. For example, a physical paymentinstrument 120 may have the name of the user 101 and/or the accountnumber of the user 101 listed on the front of the card. An examplephysical payment instrument 120 can include a magnetic stripe encodingthe physical payment instrument account information of the user 101. Inan example embodiment, the account information encoded in the magneticstripe routes payment requests to the payment processing system 140 forprocessing.

In an alternative example embodiment, the physical payment instrument120 can be a smartcard, RFID transmitter device, or any other suitablephysical device capable of initiating a transaction with the digitalwallet account of the user.

The user 101 may use the user mobile device 110 or user computing deviceto register the digital wallet application module 111, or the digitalwallet account 121 and/or access the digital wallet account 121 accountof the user 101. The user mobile device 110 may comprise appropriatetechnology that includes or is coupled to a web server (for example, aweb browser application, or other suitable application for interactingwith web page files).

The user 101 can use a web server 141 on the payment processing system140 to view, register, download, upload, or otherwise access the paymentprocessing system 140 via a website 142 and a communication network 105.The user 101 associates one or more registered payment instruments,including bank account debit cards, credit cards, gift cards, loyaltycards, coupons, offers, prepaid offers, peer-to-peer transactionaccounts, store rewards cards, or other type of payment instrument thatcan be used to make a purchase or redeem value-added services with adigital wallet account 121 of the user 101. The payment processingsystem 140 also may function as the issuer for the associated financialpayment instrument. The user's registration information is provided tothe payment processing system 140. The user 101 also may use the webserver 141 to define payment rules.

The user 101 may request a purchase from the merchant system (notpictured). In an example embodiment, the purchase is initiated by awireless “tap” of the mobile device 110 with the POS terminal. In analternative example embodiment, the purchase is initiated when the user101 enters an account identification number at the POS terminal or inthe user device 110. In another alternative example embodiment, thepurchase is initiated online with the merchant server. The purchase maybe initiated via the merchant website. In yet another alternativeexample embodiment, the purchase is initiated by use of apermanent/temporary virtual/physical token, QR code, bar code, or othersuitable machine-readable medium captured by the terminal reader. Themerchant's POS terminal can interact with an acquirer (or other thirdparty payment processing companies), the card network, the proxy cardsystem 140, and the payment instrument issuer.

Example Processes

The components of the example operating environment 100 are describedhereinafter with reference to the example methods illustrated in FIGS.2-3.

FIG. 2 is a block flow diagram depicting a method 200 for adding a userdevice 110 to a digital wallet account 121, in accordance with certainexample embodiments.

In block 205, the user 101 selects a user device to add to a digitalwallet account. User devices 110 that the user 101 may desire to add tothe digital wallet account 121 can include any of the user devices 110describe previously including, desktop computer, laptop computer, tabletcomputer, a television with one or more processors embedded thereinand/or coupled thereto, smart phone, handheld computer, personal digitalassistant (“PDA”), or any other wired or wireless, processor-drivendevice. The digital wallet account 121 may be represented on a userdevice 110 as a digital wallet application module 111, a digital walletapplication operating on a website or server, a representation on a userinterface of the payment processing system 140, or any other suitableembodiment of the digital wallet account 121.

Additionally or alternatively, the user 101 selects a physical paymentinstrument 120 or other physical tool for conducting transactions, suchas a smartcard, RFID device, to add to a digital wallet account. Forexample, the physical payment instrument 120 may be card for accessing aproxy card account of the user 101. Throughout the specification,“digital wallet application module 111” will be intended to encompassall embodiments of the digital wallet account on user devices 110,including physical payment instruments 102. Additionally, “user devices110” will be intended to encompass all suitable devices used to host adigital wallet account 121 embodiment, including physical paymentinstruments 102.

In block 210, the user installs a digital wallet application module 111on a user device 110. The digital wallet application module 111 can bedownloaded from a web server such as the web server 141 of the paymentprocessing system 140. The digital wallet application module 111 maycome installed on a new user device 110. The digital wallet applicationmodule 111 can be obtained from any other suitable source, such as awebsite on the Internet or a portable storage device such as a flashdrive.

In block 215, the user device 110 transmits a setup request to thepayment processing system 140. A request for adding a user device 110 isrequired when a digital wallet application module 111 is first installedand after each reset. Thus, the first activation is when the digitalwallet application module 111 is first set up on the user device 110. Asubsequent reset and re-activation of the digital wallet applicationmodule 111 will be considered a new activation. In an exampleembodiment, re-activation of a deactivated device 110 is performed byreinstalling and setting up the digital wallet application module 111 onthe user device 110. In an example embodiment, the user 101 may berequired to re-enter financial payment card information.

The digital wallet application module 111 can be installed on a userdevice 110 before being associated with a digital wallet account 121.

In block 220, the digital wallet application module 111 on the userdevice 110 is authorized by the user 101. In an example embodiment theuser 101 must enter an authorization for the setup to be initiated bythe payment processing system 140. That is, the payment processingsystem 140 can require a username and password, or other suitableauthorization protocol, to begin the setup process for the digitalwallet application module 111. In alternate example embodiments, theauthorization of the user 101 can be required at any point of the setupprocess, such as before the installation of the digital walletapplication module 111 or after the setup process has begun.

In block 225, the user device 110 is added to the list of devices on thedigital wallet account 121. In an example embodiment, a page on a userinterface of the digital wallet account 121 provides a listing of userdevices associated with the digital wallet account 121. The devicelisting will indicate the enabled user devices 110 that the user ownsand the activation state of each user device 110. The device listcontains all of the information required to render a virtualrepresentation of the user device 110 to the user 101. For example, thedevice list may show information indicating the device status such asthe device 110 name, the activation date, the last time a transactionwas initiated, the activation status, a device image, an option todeactivate any active devices 110, an option to retry a deactivation ifa previous attempt did not complete, and any other suitable displays oroptions.

In an example embodiment, the user 101 can access the digital walletaccount 121 by logging onto the payment processing system website 142online, using a digital wallet application module 111 on a mobile usercommunication device such as a user device 110, or by using any othersuitable user interface system. The user 101 may retrieve the status ofall devices linked to the digital wallet account.

The user 101 can select a user device 110 to add to the digital walletaccount 121 by adding the user device 110 details into a user interfaceon the digital wallet account 121. For example, the user 101 can enterthe phone number to a mobile user device 110 and the digital walletaccount 121 can locate the appropriate user device 110 over the network105, via email, over a wired network, or via any other suitable manner.The user 101 can select the user device 110 from a list of devicesassociated with the user 101. The user 101 can select a user device 110from a list of inactive devices. Any other suitable manner of selectinguser devices to add to the digital wallet account can be employed.

If the digital wallet account 121 attempts to set up a new user device110 that has not had the digital wallet application module 111installed, then the digital wallet 121 can initiate installation. Forexample, the digital wallet account 121 can transmit the digital walletapplication module to the user device. In another example, the userdevice can locate the digital wallet application on the Internet anddownload the application. Any other method can be utilized to installthe digital wallet application module 111.

The device list can display the user device 110 with any additionalidentification or visual representations of the user device 110 that areconfigured by the user 101 or the digital wallet account 121. Forexample, the device list can display the user device phone number,serial number, username, or any suitable alias or identificationprovided by the user or others. The device list can display a picture orother representation of the user device 110, such as a picture of themodel of the user device 110 based on provided model numbers. Any othersuitable display or identification can be used to represent the userdevice on the device list.

FIG. 3 is a block flow diagram depicting a method 300 for removing auser device 110 from a digital wallet account 121, in accordance withcertain example embodiments.

The user 101 can select a user device 110 that the user 101 no longerwants to have associated with the digital wallet account 121. The usercan desire to remove a user 110 device if the device is stolen, lost, orotherwise has the security of the user device 110 compromised. The user101 can desire to remove a user device 110 if the user device 110 isbeing traded, sold, or replaced. The user 101 can desire to remove auser device 110 if the user device 110 is no longer going to be used fordigital transactions or for any other suitable reason.

In block 310, the user 101 can open the device list on a user interfaceof the digital wallet account 121 in the manner employed to add a userdevice 110. The user can access the digital wallet account 121 bylogging onto the payment processing system website 142 online, using adigital wallet application module 111 on a user device 110, or by usingany other suitable user interface system associated with the digitalwallet account 121.

In block 315, the user 101 can select a user device 110 to remove fromthe device list. The user 101 can identify the desired user device 110by selecting the representation of the user device 110 from the list.For example, the user 101 can click on a picture of the user device 110on the user interface. The user 101 can tap a username or identifier ofthe user device 110 on the user interface. The user 101 can state averbal identification of the user device 110 to select the device. Anyother suitable manner of selecting the user device 110 from the list canbe employed.

In block 320, the digital wallet account 121 deactivates the user device110. When deactivation is initiated, the digital wallet account 121 userinterface being utilized transmits the deactivation request to thepayment processing system 140 and the user device 110 that is beingdeactivated. The payment processing system 140 can receive the requestand deactivate the user device 110. The payment processing system 140will no longer honor requests for transactions from the digital walletapplication module 111 operating on the user device.

In an example, a transaction is attempted with the digital walletapplication module 111 of a user device 110 that has been deactivated onthe payment processing system 140. The payment processing system 140 canreceive a transaction request and recognize that the user device 110being used in the transaction has been deactivated by the user 101. Thepayment processing system 140 can recognize an identity of the userdevice 110 or other identifier included in the transaction details. Whenthe payment processing system 140 recognizes an identity of adeactivated user device 110, the payment processing system 140 canrefuse the transaction. The payment processing system 140 canadditionally alert the user 101, the digital wallet account 121, orother party of the attempted transaction for the purposes of fraudprevention.

The digital wallet account 121 user interface being utilized todeactivate a user device 110 transmits the deactivation request to theuser device 110 that is being deactivated. If the user device 110 issuccessfully contacted, then the user device 110 is deactivated and thedigital wallet application module 111 can no longer be utilized fortransactions using the digital wallet account 121 of the user 101.

In block 325, the digital wallet application module 111 is removed fromthe user device 110 that has been deactivated. Upon receiving thedeactivation request from the digital wallet account 121, the digitalwallet application module 111 can disable the account of the user on thedigital wallet application module 111 by executing the instructionsprovided by the digital wallet account 121. Additionally oralternatively, the digital wallet application module 111 can be removedfrom a user device 110 that has been deactivated from the digital walletaccount 121 by executing the instructions provided by the digital walletaccount 121. In an example embodiment, the digital wallet account 121can transmit instructions to the user device 110 to delete the digitalwallet application module 111, to delete the digital wallet accountinformation, to delete financial account information from the userdevice 110, or to delete any other suitable information that can be usedto make the digital wallet application module 111 operable with thedigital wallet account 121 of the user. Upon receipt, the digital walletapplication module 111 can execute the instructions. Additionally oralternatively, the user 101 can manually delete the digital walletapplication module 111 or other information from the user device 110.

If the digital wallet account 121 is unable to contact the user device110 at the time of deactivation, then the deactivation can occur whenthe user device 110 next achieves network access. That is, when the userdevice 110 is again turned on, returned to a service area, or otherwiseachieves a network connection, the instructions can be transmitted atthat time.

In certain instances, the user device 110 may be partially disabled. Apartially disabled state can be created when the payment processingsystem 140 can be updated, but not the user device 110. When the digitalwallet account 121 is unable to contact the user device 110, the digitalwallet application module 111 on the user device cannot be deleted ordisabled. Moreover, if the user 101 has a stored value card on a userdevice 110 that is partially disabled, then the user 101 may stillvulnerable to charges on the stored value card, and the user 101 willneed to contact the issuer of the stored value card to disable the card.The user interface will display to the user 101 that the digital walletaccount 121 will retry the deactivation button until a completedeactivation is achieved or the digital wallet account 121 is requestedto discontinue the deactivation.

In block 330, the user interface shows the status of the deactivation ofthe user device 110. The user interface will provide a clear indicationto the user of what is happening, and what, if any, further action mustbe taken. The user interface displays to the user that the deactivationis successful, if the deactivation is in progress, if the user device110 has been partially disabled, or any other suitable status.

The user interface will also allow the user 101 to remove anydeactivated user devices 110 from the list of devices, or the removalcan occur automatically. User devices 110 that have been deactivated canappear in the list in a disabled state until the user 101 manuallydeletes them. Additionally or alternatively, the user 101 can leave thedeactivated devices on the list of devices or store the deactivated userdevice 110 in a list of deactivated or unused devices.

Additionally or alternatively, the deactivated user device 110 canremain on the list of devices but remain hidden from view until the user101 requests that hidden devices be displayed. In an example embodiment,user devices 110 that are marked hidden will not be shown, except whenshowing a historic device view is requested.

If a user device 110 has been deactivated on the digital wallet account121 at the payment processing system 140 but not the digital walletapplication module 111 on the user device 110 has not been deactivated,a transaction can be attempted by a person in possession of the userdevice 110. For example, if a user device 110 is stolen, the person withthe stolen user device 110 may attempt a transaction. The paymentprocessing system 140 is notified of the transaction request. However,the payment processing system 140 determines that the user 101 requestedto have the user device 110 deactivated on the user device list. Thepayment processing system 140 declines the transaction and attemptsagain to deactivate the digital wallet application module 111 on theuser device.

Example Systems

FIG. 4 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid sate drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCI”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of, allof, or to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, biometricreaders, electronic digitizers, sensors, receivers, touchpads,trackballs, cameras, microphones, keyboards, any other pointing devices,or any combinations thereof. The I/O interface 2060 may couple thecomputing machine 2000 to various output devices including videodisplays, speakers, printers, projectors, tactile feedback devices,automation control, robotic components, actuators, motors, fans,solenoids, valves, pumps, transmitters, signal emitters, lights, and soforth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with a opportunity to control whether programs orfeatures collect user information (e.g., information about a user'ssocial network, social actions or activities, profession, a user'spreferences, or a user's current location), or to control whether and/orhow to receive content from the content server that may be more relevantto the user. In addition, certain data may be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed previously. The systems, methods, and procedures describedherein can be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the inventions claimedherein.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

What is claimed is:
 1. A computer-implemented method to deactivate userdevices from digital wallet accounts, comprising: associating, using oneor more computing devices, one or more user computing devices with adigital wallet account of a user, each of the associated one or moreuser computing devices being activated to conduct financial transactionswith a merchant utilizing the digital wallet account; presenting, usingthe one or more computing devices, the associated user computing devicesin a list of associated user computing devices; receiving, using the oneor more computing devices, a request to deactivate a particular usercomputing device from the list of associated user computing devices;deactivating, using the one or more computing devices, the particularuser computing device, the deactivation being sufficient to prevent theuser computing device from conducting transactions with a merchantutilizing the digital wallet account; and presenting, using the one ormore computing devices, a deactivated status of the particular usercomputing device.
 2. The computer-implemented method of claim 1, whereinthe deactivating of the particular user computing device compriseslogging the particular user computer device as deactivated such that apayment authorization request comprising an identification of theparticular user computing device will be rejected.
 3. Thecomputer-implemented method of claim 1, wherein the deactivating of theparticular user computing device comprises communicating instructions tothe particular user computing device to disable an applicationassociated with the digital wallet account on the particular usercomputing device.
 4. The computer-implemented method of claim 1, whereinthe deactivating of the particular user computing device comprisescommunicating instructions to the particular user computing device toremove an application associated with the digital wallet account on theparticular user computing device from the particular user computingdevice.
 5. The computer-implemented method of claim 1, wherein the listof associated user computing devices is presented via a user interfaceof an application on a user device.
 6. The computer-implemented methodof claim 1, wherein the deactivated user device is removed from the listof associated user devices.
 7. The computer-implemented method of claim1, wherein the particular user computing device is a mobile computingdevice, a magnetic stripe card, an RFID device, a smartcard, or anaccount identifier capable of being scanned.
 8. The computer-implementedmethod of claim 1, wherein the digital wallet account is managed by apayment processing computing system.
 9. A computer program product,comprising: a non-transitory computer-readable storage device havingcomputer-readable program instructions embodied thereon that whenexecuted by a computer perform a method to deactivate user devices fromdigital wallet accounts, the computer-readable program instructionscomprising: computer program instructions to associate one or more usercomputing devices with a digital wallet account of a user, each of theassociated one or more user computing devices being activated to conductfinancial transactions with a merchant utilizing the digital walletaccount; computer program instructions to present the associated usercomputing devices in a list of associated user computing devices;computer program instructions to receive a request to deactivate aparticular user computing device from the list of associated usercomputing devices; and computer program instructions to deactivate theparticular user computing device, the deactivation being sufficient toprevent the user computing device from conducting transactions with amerchant utilizing the digital wallet account.
 10. The computer programproduct of claim 9, wherein the deactivating of the particular usercomputing device comprises logging the particular user computer deviceas deactivated such that a payment authorization request comprising anidentification of the particular user computing device will be rejected.11. The computer program product of claim 9, wherein the deactivating ofthe particular user computing device comprises communicatinginstructions to the particular user computing device to disable anapplication associated with the digital wallet account on the particularuser computing device.
 12. The computer program product of claim 9,wherein the deactivating of the particular user computing devicecomprises communicating instructions to the particular user computingdevice to remove an application associated with the digital walletaccount on the particular user computing device from the particular usercomputing device.
 13. The computer program product of claim 9, whereinthe list of associated user computing devices is presented via a userinterface of an application on a user device.
 14. The computer programproduct of claim 9, further comprising computer program instructions topresent a deactivated status of the particular user computing device.15. The computer program product of claim 9, wherein the particular usercomputing device is a mobile computing device, a magnetic stripe card,an RFID device, a smartcard, or an account identifier capable of beingscanned.
 16. A system to deactivate user devices from digital walletaccounts, the system comprising: a storage resource; a network module;and a processor communicatively coupled to the storage resource and thenetwork module, wherein the processor executes application codeinstructions that are stored in the storage resource and that cause thesystem to: associate one or more user computing devices with a digitalwallet account of a user, each of the associated one or more usercomputing devices being activated to conduct financial transactions witha merchant utilizing the digital wallet account; present the associateduser computing devices in a list of associated user computing devices;receive a request to deactivate a particular user computing device fromthe list of associated user computing devices; and deactivate theparticular user computing device, the deactivation being sufficient toprevent the user computing device from conducting transactions with amerchant utilizing the digital wallet account.
 17. The system of claim16, the instructions further comprising presenting a deactivated statusof the particular user computing device.
 18. The system of claim 16,wherein the deactivating of the particular user computing devicecomprises logging the particular user computer device as deactivatedsuch that a payment authorization request comprising an identificationof the particular user computing device will be rejected.
 19. The systemof claim 16, wherein the deactivating of the particular user computingdevice comprises communicating instructions to the particular usercomputing device to disable an application associated with the digitalwallet account on the particular user computing device.
 20. The systemof claim 16, wherein the deactivating of the particular user computingdevice comprises communicating instructions to the particular usercomputing device to remove an application associated with the digitalwallet account on the particular user computing device from theparticular user computing device.